Systems and methods of profiling power cycles in a battery for indicating detrimental battery operation

ABSTRACT

Systems and methods for profiling power cycle characteristics in a device powered at least by a battery are disclosed. In one embodiment, the method comprises the steps of: detecting a series of power cycle events, examining the series of power cycle events for at least one indication of reduced life of the battery; storing the indication; and notifying a user of the device about the indication. Each power cycle event indicates a transition between line power and battery power.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation application claiming priority andbenefit under 35 USC §120 from U.S. patent application Ser. No.11/428,348, filed Jun. 30, 2006, now U.S. Pat. No. 7,504,801 B2.

FIELD OF THE DISCLOSURE

The present disclosure relates to electronic devices, and morespecifically, to systems and methods for power management of electronicdevices.

BACKGROUND

Some electronics devices are able to operate from either alternatingcurrent (AC), also known as line power, or a battery. In such devices,as long as line power is provided, the device operates on line power andrecharges the battery. When line power is removed, the device operateson battery power, and the battery discharges until line power is onceagain provided.

Repeatedly using the battery rather than line power to operate thedevice reduces the lifetime of the battery, because powering the devicefrom the battery discharges the battery, and battery lifetime is limitedto some number of charge/discharge cycles. Sometimes a user removes linepower from the device without realizing that doing so will negativelyaffect the battery lifetime. One example of this situation occurs whenline power to the device is used in conjunction with a switch, such as alight switch or the switch on a power strip.

In this configuration, a user may turn off the switch, and thus linepower to the device, without realizing the device is affected. Duringthe time that the switch is off, battery-powered devices will depletetheir battery charge. This has the effect of reducing battery life ifdone repeatedly. Another effect is that the device battery will be in alower state of charge if a true power outage were to occur. This isparticularly true for devices which rely on battery operation to delivera critical service, such as when a device interfaces to the telephonenetwork or an alarm system.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the disclosure can be better understood with referenceto the following drawings. The components in the drawings are notnecessarily to scale, emphasis instead being placed upon clearlyillustrating the principles of the present disclosure.

FIG. 1 is a block diagram of an environment in which one embodiment of asystem and method for profiling power cycles in an electronics device islocated.

FIG. 2 is a block diagram of an environment in which an alternativeembodiment of a system and method for profiling power cycles in anelectronics device is located.

FIG. 3 is a flowchart describing an exemplary method embodied by powerinterruption logic 140 from FIG. 1.

FIG. 4 illustrates how power cycle characteristics are derived from aseries of power cycle events in one embodiment of power interruptionlogic 140 from FIG. 1.

FIG. 5 is a data flow diagram illustrating how power interruption logic140 (from FIG. 1) is partitioned between a device and a managementsystem in one embodiment.

FIG. 6 is a data flow diagram illustrating another partitioning of powerinterruption logic 140 between a device and a management system.

FIG. 7 is a data flow diagram illustrating yet another partitioning ofpower interruption logic 140 between a device and a management system.

FIG. 8 is a data flow diagram illustrating another partitioning of powerinterruption logic 140 between a device and a management system.

FIG. 9 depicts one example of a power characteristics profile.

FIG. 10 is a flowchart illustrating a process of comparing power cyclecharacteristics to one or more profiles, as performed by one embodimentof power interruption logic 140.

FIG. 11 illustrates an example scenario in which power cyclecharacteristics are compared to three profiles.

DETAILED DESCRIPTION

The embodiments disclosed herein provide systems and methods forprofiling power cycles in an electronics device. In one such embodiment,a series of power cycles in the device is detected. The series of powercycles is characterized and described in terms of attributes such as thefrequency of transitions to battery, the total number of transitions,and the duration of the battery power interval between transitions. Thepower cycle characteristics are analyzed to determine if thecharacteristics indicate detrimental battery operation in the device.For example, a transition to battery power approximately every 24 hoursmay be found to indicate a situation that reduces battery life. If suchan indication is found, the indication is stored and may be used tonotify the user of the device, or a system manager.

One typical result of detrimental battery operation is reduced batterylife. Another is an increased likelihood that the battery is in apartially discharged state. Other conditions that are detrimental to thebattery's electrical characteristics are also contemplated as being inthe scope of detrimental battery operation.

FIG. 1 is a block diagram of an environment in which one embodiment of asystem and method for profiling power cycles in an electronics device islocated. A device 100 is supplied with power by power supply 110, whichconverts AC power received from outlet 120 to DC power. Device 100includes a battery 130, which supplies DC power to power interruptionlogic 140 and other electronic components within device 100 when ACpower to power supply 110 is interrupted. This feature is commonly knownas “battery backup.”

One reason for such an interruption is a user turning off a first switch150 which optionally controls the AC power being delivered by outlet 120and the DC power being delivered by power supply 110. Another reason forsuch an interruption is a user turning off a second switch 160 whichoptionally controls the DC power being delivered by power supply 110.Other exemplary reasons for power interruption include a blackout on thepower distribution grid supplying power to outlet 120, and a userunplugging power supply 110 from outlet 120.

When power flows normally from power supply 110, battery controllerlogic 170 uses this DC power to charge battery 130. When batterycontroller logic 170 detects an interruption in power from power supply110, battery controller logic 170 effects the switchover to batterypower. In one implementation, battery controller logic 170 and battery130 are integrated into a battery module 180.

FIG. 2 is a block diagram of an environment in which an alternativeembodiment of a system and method for profiling power cycles in anelectronics device is located. A management system 210 is incommunication with device 100 over a communication channel 220. In thisembodiment, a portion (140A) of power interruption logic 140 resides indevice 100 and another portion (140B) resides in management system 210.In one embodiment, device 100 is a multimedia terminal adapter (MTA)located at a customer premises, management system 210 is located at theheadend of a service operator, and communication channel 220 is providedby a physical media, such as a hybrid fiber coax (HFC) cable.

As will be described in further detail below, power interruption logic140 detects transitions within device 100 between AC power and batterypower, and examines these transitions for characteristics which indicatedetrimental battery operation such as reduced battery charge. If suchcharacteristics are found, power interruption logic 140 generates, andoptionally stores, an error.

Exemplary ways of partitioning power interruption logic 140 betweendevice 100 and management system 210 will be discussed later inconnection with FIGS. 5-8. Power interruption logic 140 can beimplemented in software, hardware, or a combination thereof. In someembodiments, power interruption logic 140 is implemented in softwarethat is stored in a memory and that is executed by a suitablemicroprocessor situated in a computing device. In alternativeembodiments, the power interruption logic 140 is implemented inhardware, including but not limited to: a discrete logic circuit(s)having logic gates for implementing logic functions upon data signals; afield programmable gate array (FPGA) having appropriate sequentialand/or combinatorial logic gates; and an application specific integratedcircuit (ASIC) having appropriate sequential and/or combinatorial logicgates. In other embodiments, power interruption logic 140 is implementedby a combination of software and hardware.

FIG. 3 is a flowchart describing an exemplary method embodied by powerinterruption logic 140. The process 300 begins at block 310, whichdetects a power cycle event. In one implementation, this power cycleevent detected through an interrupt mechanism; in anotherimplementation, the event is detected through a polling mechanism.Examples of power cycle events are transitions between AC power andbattery power, and battery depletions. One of ordinary skill in the artshould understand that the event may be viewed from the standpoint ofthe battery, or the AC power supply. That is, a transition from AC tobattery may be denoted as SWTICH_TO_BATTERY or SWITCH_FROM_AC.

Processing continues at block 320, where information about the powercycle event, such as the occurrence time and event type (for example,AC-to-battery or battery-to-AC), is stored. Next (block 330), the seriesof stored events is analyzed to determine at least one power cyclecharacteristic. (Power cycle characteristics will be discussed in moredetail in connection with FIG. 4.)

At block 340, the process determines whether the observed power cyclecharacteristic(s) indicate detrimental operation of battery 130. In oneembodiment, this determination is made by comparing thecharacteristic(s) to a threshold. In another embodiment, thisdetermination is made by comparing the characteristic(s) to multiplethresholds, where a different indication is produced for each threshold.In this manner, different levels of reduced lifespan can be indicated,for example, a Severe or Error indication for one threshold, a Warningindication for another threshold, and an Informational indication foryet another threshold.

If the observed power cycle characteristic(s) does not indicatedetrimental battery operation, processing continues at block 310,awaiting detection of another power cycle event. If reduced lifespan isindicated, the indication is optionally stored at block 350, andoptionally reported (at block 360) by a visual or audio alert to theuser of device 100 (e.g., a warning LED or a beep tone). Other examplesof reporting methods will be discussed in connection with FIG. 5.Processing then continues at block 310, awaiting detection of anotherpower cycle event.

FIG. 4 illustrates how power cycle characteristics 400 are derived froma series of power cycle events in one embodiment of power interruptionlogic 140. Power cycle events 410A1 and 410A2 represent transitions frombattery power to AC power. Events 410B1, 410B2 and 410B3 representtransitions from AC power to battery power. Event 410D1 indicates thatthe battery has been depleted and the device has entered a powered-offstate.

The interval between transitions to battery power is one examplecharacteristic derived from this series of power cycle events 410.Transition interval 420B2 is the interval between transition 410B1 andtransition 410B2. Transition 420B3 is the interval between transition410B2 and transition 410B3.

In one embodiment, an average interval between transitions is calculatedas power cycle data is collected. This average interval between powercycle transitions can also be viewed as an average frequency (430) ofpower cycle transitions, and the term “frequency” will be usedhereinafter instead of “interval between.”

Yet another characteristic derivable from power cycle events 410 is thevariation (440) in frequency of power cycle transitions. Two commonmethods for calculating variation are standard deviation and variance.Other power cycle characteristics include a total number (450) oftransitions to battery power, and a total number of battery depletions(470) which have occurred.

The duration of battery power in between transitions is another examplecharacteristic derived from power cycle events 410. Duration 460B2 isthe duration of battery power for the interval between transition 410B1and transition 410B2. Duration 460B3 is the duration of battery powerfor the interval between transition 410B2 and transition 410B3. In oneembodiment, an average duration of battery power 470 is maintained aspower cycle data is collected.

One of ordinary skill in the art should understand that these, andother, power cycle characteristics can be used alone or in anycombination by various embodiments of power interruption logic 140.

FIG. 1 illustrated an embodiment in which power interruption logic 140is located in device 100. FIG. 2 illustrated an embodiment in whichpower interruption logic 140 is divided between device 100 andmanagement system 210. FIGS. 5-8 are data flow diagrams illustrating howpower interruption logic 140 is partitioned between device 100 andmanagement system 210 in four exemplary embodiments.

In the embodiment of FIG. 5, device 100 detects (310) power cycleevents, analyzes (330) events to determine power cycle characteristics400, and determines (340) an indication of detrimental batteryoperation, based on the characteristics. (These areas of functionalitywere described earlier in connection with FIG. 3.) Upon determining thatpower cycle characteristics 400 are an indication of detrimental batteryoperation, device 100 notifies management system 210 using message 510.Management system 210 logs (520) an error, which may include logging anidentifier of device 100, the time the error indication was received,and the type of error indication.

Next, notification logic (530) within management system 210 determineswhether the user of device 100 should be notified about the indicationof detrimental battery operation, and if so, what mechanism is to beused. For example, some customers may not want to be notified at all,some may prefer email, and others may prefer a phone call. If thenotification method involves device 100, management system 210 sends amessage (540) to device 100, instructing device 100 to alert the userthat detrimental battery operation has been indicated.

One example of notification involving device 100 is when device 100provides a visual and/or electrical alarm block indicators to the userand activates the visual and/or electrical alarm. Another example iswhen a case in which device 100 causes an indication to be displayed onthe user's television or computer screen.

In the embodiment of FIG. 6, device 100 detects (310) power cycle eventsand reports the events to management system 210 using message 610.Management system 210 analyzes (330) events to determine power cyclecharacteristics 400, and determines (340) an indication of detrimentalbattery operation, based on the characteristics. If detrimental batteryoperation is indicated, management system 210 logs (620) an error, andnotification logic 630 determines whether the user of device 100 shouldbe notified about the indication of detrimental battery operation, andif so, what mechanism is to be used. If the notification method involvesdevice 100, management system 210 sends a message (550) to device 100,instructing device 100 to alert the user that detrimental batteryoperation has been indicated.

The embodiments of FIGS. 7 and 8 use power characteristic profiles 900in determining an indication of detrimental battery operation. A profile900, which will be discussed in more detail in connection with FIG. 9,describes the characteristics of a series of power cycles, for example,in terms of power cycle frequency and/or battery interval duration. Inthe embodiment of FIG. 7, profiles 900 reside in management system 210.In the embodiment of FIG. 8, profiles 900 are downloaded to device 100.

In the embodiment of FIG. 7, device 100 detects (310) power cycleevents, and analyzes (330) events to determine power cyclecharacteristics 400. Device 100 communicates the power cyclecharacteristics 400 to management system 210 through message 710.Management system 210 compares (720) the power cycle characteristics 400to a set of profiles 900 maintained by management system 210. A matchingprofile is an indication of detrimental battery operation.

If detrimental battery operation is indicated, management system 210logs (730) an error, and notification logic 740 determines whether theuser of device 100 should be notified about the indication ofdetrimental battery operation, and if so, what mechanism is to be used.If the notification method involves device 100, management system 210sends a message (750) to device 100, instructing device 100 to alert theuser that detrimental battery operation has been indicated.

In the embodiment of FIG. 8, management system 210 provides one or moreprofiles 900 to device 100. Once profiles 900 are downloaded, device 100detects (310) power cycle events, and analyzes (330) events to determinepower cycle characteristics 400. In this embodiment, device 100 compares(810) the power cycle characteristics 400 to the set of profiles. Amatching profile is an indication of detrimental battery operation, inwhich case device 100 notifies management system 210 using message 820.

On receipt of message 820, management system 210 logs (830) an error.Next, notification logic (840) within management system 210 determineswhether the user of device 100 should be notified about the indicationof detrimental battery operation, and if so, what mechanism is to beused. If the notification method involves device 100, management system210 sends a message (850) to device 100, instructing device 100 to alertthe user that detrimental battery operation has been indicated.

In some embodiments, different profiles 900 are used for different typesof devices, or for different types of batteries, or for differentdevice/battery combinations. This is useful because batteries differwith regard to power characteristics (e.g., the number of lifetimecycle/discharge cycles, the amount of voltage that constitutes a deepand shallow discharge) and devices differ in battery usage parameters(e.g., how much voltage/current is drawn by the device). In some ofthese embodiments, these profiles 900 are created by a user ofmanagement system 210.

The power characteristic profiles 900 used by the embodiments of FIGS. 7and 8 will now be discussed in further detail in connection with FIGS. 9and 10. FIG. 9 depicts an exemplary power characteristics profile 900.Profile 900 has a descriptive name 910 and one or more characteristics920, where a characteristic 920 comprises an attribute 930 and athreshold value 940. Example attributes 930 include an average frequencyof transitions to battery, a variation in frequency of transitions tobattery, an average interval between transitions to battery, and a totalnumber of transitions to battery. In one embodiment, the threshold value940 is used in comparing a profile 900 to analyzed power characteristics400, as will be described later in connection with FIG. 10.

In one embodiment, a profile includes a combinational set of criteria,for example, Characteristic A AND Characteristic B BUT NOTCharacteristic C. In another embodiment, a profile includes a sequenceof characteristics occurring over time, for example, Characteristic Afollowed by Characteristic B within C minutes. One of ordinary skill inthe art should be able to devise profiles suitable to detect conditionsappropriate to the indication of detrimental battery operation.

Also associated with profile 900 is a severity level 950, for example,Informational, Warning and Error. Severity 950 is used in determiningwhether to notify the user of device 100, and in what manner. In oneexample embodiment, an indication of detrimental battery operation whichhas a severity of Error is reported to a user with an intrusivemechanism such as a phone call, an indication which is a WarningInformational is reported with a less intrusive mechanism such as ane-mail message, and a Warning indication is not reported to the user.

FIG. 10 is a flowchart illustrating an exemplary process of comparingpower cycle characteristics 400 to one or more profiles 900, inaccordance with one embodiment of the systems and methods of profilingpower cycles in an electronics device. This process can be used, forexample, by the comparison logic 720 and 810 in the embodiments of FIGS.7 and 8, respectively. The process of FIG. 10 selects a best match, or“winning profile” when more than one profile matches the device powercycle characteristics.

The process begins at block 1010, where the Winning_Profile variable isinitialized to None, and the Curr_Profile variable is initialized to thefirst profile in the set. Next, at block 1020, the power cyclecharacteristics 400 of the device are compared to characteristics in thecurrent profile. Specifically, the value for each power cyclecharacteristic (e.g., frequency, duration) is compared to the threshold940 in the corresponding characteristic 920 of the current profile. Ifall values in the device characteristics exceed the thresholds in thecurrent profile, then this current profile is a match, and processingcontinues at block 1030. If all values in the device characteristics donot exceed the current profile thresholds, then this profile is not amatch, and the next profile is loaded at block 1040. If another profileexists, processing returns to block 1020. If no more profiles remain,the process exits at block 1050.

Returning to block 1030, a determination is made whether the currentprofile is a stronger indication of detrimental battery operation thanthe winning profile. The strength of a profile's indication depends onits threshold values 940. A frequency of 12 hours is a strongerindication than a frequency of 24 hours, since a device that transitionsto battery every 12 hours has a shorter battery life than a device thattransitions to battery every 24 hours. A battery duration of 8 hours isstronger than a battery duration of 4 hours, since a device that usesbattery power for 8 hours between recharges has a shorter battery lifethan one that uses battery power for 4 hours between recharges.

If the current profile is a stronger indication than the winningprofile, then processing continues at block 1060, where the currentprofile replaces the winning profile. If the current profile is not astronger indication than the winning profile, then the winning profileremains unchanged. Thus, Winning_Profile always contains the profilewith the strongest indication so far. In either case, the next profileis then loaded at block 1040, and processing returns to block 1020. Theprocess eventually ends at block 1050, after all profiles have beentested for a match, and Winning_Profile contains the best match.

The process of FIG. 10 is illustrated in the example scenario of FIG.11, which involves a set of device power cycle characteristics 400, andthree profiles, 900A, 900B, and 900C. In block 1020 of FIG. 10, valuesin the power cycle characteristics 400 are compared to correspondingthresholds in the first profile, 900A. In the scenario of FIG. 11, allthresholds are met. Specifically, when frequency average value 430 iscompared to frequency average threshold 930A1, the 22 hour value incharacteristic 400 meets the 24 hour threshold in profile 900A. Whenfrequency variation value 440 is compared to frequency variationthreshold 930A2, the 1.3 hour value in characteristic 400 meets the 2hour threshold in profile 900A. When number of transitions value 450 iscompared to number of transitions threshold 930A3, the 10 count value450 meets the 10 count threshold 930A3. Finally, when average durationvalue 470 is compared to average duration threshold 930A4, the 9.4average duration value 470 meets the average duration threshold 930A4.

Note that two of the characteristics—frequency average and frequencyvariation—are met when the value is less than the threshold. This istrue because a lower frequency of transitions to battery is a strongerindication of detrimental battery operation. In contrast, the other twocharacteristics—number of transitions and average duration—are met whenthe value is more than the threshold, because a longer battery durationis a stronger prediction of detrimental battery operation, as is ahigher number of transitions to battery.

Continuing with the example scenario of FIG. 11, since power cyclecharacteristics 400 meets all threshold criteria in the first profile900A, block 1030 of FIG. 10 is executed. Block 1030 determines whetherthe current profile is a stronger indication of detrimental batteryoperation than the winning profile. In this scenario, Winning_Profile isset to None (after being initialized in block 1010). Therefore, block1060 is executed to make the current profile, 900A, be the winningprofile.

The next profile, 900B, is selected to be the current profile in block1040, and the comparison between values in the power cyclecharacteristics 400 and corresponding thresholds in profile 900B occursin block 1020. In this example scenario, all thresholds in profile 900Bare met, so block 1030 is executed. In this scenario, the currentprofile, 900B, is not a stronger indication than the winning profile,900A: the number of transitions threshold 930B3 in the current profile900B is 9, which is less than 10, the number of transitions threshold930A3 in the winning profile 900A. Since the comparison failed, block1040 is executed next and the winning profile remains the same.

The next profile, 900C, is selected to be the current profile in block1040. The comparison between values in the power cycle characteristics400 and corresponding thresholds in profile 900C occurs in block 1020.In this example scenario, all thresholds in profile 900C are not met:the number of transitions 340 in characteristics 400 is 10, which isless than 400, the number of transitions threshold 930C3 in the currentprofile 900C. Therefore, block 1040 is executed and the winning profileremains the same. Since the current profile 900C is the last profile,block 1050 is executed next and processing is complete.

In this scenario, the process of FIG. 10 has selected profile 900A asthe “winning profile” and best match from all three profiles. Theseverity level 950 of winning profile 900A can then be used, asdescribed earlier in connection with FIG. 9, to determine whichnotification mechanism is used. For example, the severity level 950 ofwinning profile 900A can be used by the notification logic 740 and 850in the embodiments of FIGS. 7 and 8, respectively.

Any process descriptions or blocks in flowcharts should be understood asrepresenting modules, segments, or portions of code which include one ormore executable instructions for implementing specific logical functionsor steps in the process. As would be understood by those of ordinaryskill in the art of the software development, alternate implementationsare also included within the scope of the disclosure. In these alternateimplementations, functions may be executed out of order from that shownor discussed, including substantially concurrently or in reverse order,depending on the functionality involved.

The systems and methods disclosed herein can be embodied in anycomputer-readable medium for use by or in connection with an instructionexecution system, apparatus, or device. Such instruction executionsystems include any computer-based system, processor-containing system,or other system that can fetch and execute the instructions from theinstruction execution system. In the context of this disclosure, a“computer-readable medium” can be any means that can contain, store,communicate, propagate, or transport the program for use by, or inconnection with, the instruction execution system. The computer readablemedium can be, for example but not limited to, a system or propagationmedium that is based on electronic, magnetic, optical, electromagnetic,infrared, or semiconductor technology.

Specific examples of a computer-readable medium using electronictechnology would include (but are not limited to) the following: anelectrical connection (electronic) having one or more wires; a randomaccess memory (RAM); a read-only memory (ROM); an erasable programmableread-only memory (EPROM or Flash memory). A specific example usingmagnetic technology includes (but is not limited to) a portable computerdiskette. Specific examples using optical technology include (but arenot limited to) an optical fiber and a portable compact disk read-onlymemory (CD-ROM).

The foregoing description has been presented for purposes ofillustration and description. It is not intended to be exhaustive or tolimit the disclosure to the precise forms disclosed. Obviousmodifications or variations are possible in light of the aboveteachings. The implementations discussed, however, were chosen anddescribed to illustrate the principles of the disclosure and itspractical application to thereby enable one of ordinary skill in the artto utilize the disclosure in various implementations and with variousmodifications as are suited to the particular use contemplated. All suchmodifications and variation are within the scope of the disclosure asdetermined by the appended claims when interpreted in accordance withthe breadth to which they are fairly and legally entitled.

What I claim is:
 1. A method comprising: detecting a series of powercycle events, each power cycle event indicating a transition betweenline power and battery power; analyzing, by a computing device thatincludes at least one processor, the series of power cycle events toproduce at least one power cycle characteristic; comparing the powercycle characteristic to at least one stored power cycle characteristicprofile, which includes an average frequency of transitions to batterycharacteristic, an average interval between transitions to batterycharacteristic, and a total number of transitions to batterycharacteristic; and storing in memory an indication of detrimentalbattery operation if the comparison is a match, wherein a determinationis made whether to notify an individual of the detrimental batteryoperation based on settings provided by the individual, and wherein ane-mail notification is provided to the individual to identify thedetrimental battery operation.
 2. The method of 1, wherein the at leastone power cycle characteristic comprises a frequency of power cycleevents, a duration of a battery power interval, a total number of powercycle events, and a variation in the frequency of power cycle events. 3.The method of 1, further comprising the step of: notifying a user of thedevice, through a telephone call, of the indication of detrimentalbattery operation.
 4. The method of 1, further comprising the steps of:receiving a power cycle characteristics profile; and storing the powercycle characteristics profile.
 5. The method of 1, further comprisingthe steps of: creating the power cycle characteristics profile based ona description of the profile.
 6. A method comprising: detecting a seriesof power cycle events, each power cycle event indicating a transitionbetween line power and battery power; analyzing, by a computing devicethat includes at least one processor, the series of power cycle eventsto produce at least one power cycle characteristic; comparing the powercycle characteristic to at least one stored power cycle characteristicprofile, which includes an average frequency of transitions to batterycharacteristic, an average interval between transitions to batterycharacteristic, and a total number of transitions to batterycharacteristic; and producing an indication of detrimental batteryoperation if the comparison is a match, wherein a determination is madewhether to notify an individual of the detrimental battery operationbased on settings provided by the individual, and wherein an e-mailnotification is provided to the individual to identify the detrimentalbattery operation.
 7. The method of claim 6, wherein the at least onepower cycle characteristic comprises a frequency of power cycle events,a duration of a battery power interval, a total number of power cycleevents, and a variation in the frequency of power cycle events.
 8. Themethod of claim 6, further comprising the step of: notifying a user ofthe device of the indication of detrimental battery operation.
 9. Themethod of claim 6, further comprising the step of: notifying a user ofthe device, through a telephone call, of the indication of detrimentalbattery operation.
 10. The method of claim 6, further comprising thesteps of: receiving a power cycle characteristics profile; and storingthe power cycle characteristics profile.
 11. The method of claim 6,further comprising the steps of: creating the power cyclecharacteristics profile based on a description of the profile.
 12. Themethod of claim 6, further comprising the step of storing an indicationof detrimental battery operation if the comparison is a match.